Produce symbols package and deterministic builds#64
Produce symbols package and deterministic builds#64Rob-Hague wants to merge 1 commit intoquestdb:mainfrom
Conversation
📝 WalkthroughWalkthroughThe pull request updates the NuGet package project file to replace deprecated licensing configuration with modern alternatives, adds packaging metadata enhancements including README documentation and symbol packages, and introduces CI build detection for continuous integration environments. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
No actionable comments were generated in the recent review. 🎉 🧹 Recent nitpick comments
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
These options improve the debugging experience of the library using Source Link (https://learn.microsoft.com/dotnet/standard/library-guidance/sourcelink). When packaging the library, an additional .snpukg "symbol package" file is produced alongside the .nupkg, both of which would be published to nuget.org.
viewing the package in NuGet Package Explorer before:
and after:
I do not believe azure-binaries-pipeline.yml needs any changes, but I have obviously not tested it.
Summary by CodeRabbit